Method and system for scheduling and transmitting messages

ABSTRACT

A method and system for scheduling and transmitting messages is disclosed. The method and system comprise storing a plurality of audio files in an audio database, generating a schedule of queued messages via the plurality of audio files, transmitting the queued messages based on the schedule, reconfiguring the schedule based on a user interaction delivering the queued messages in accordance with the reconfigured schedule. Through the use of the method and system in accordance with the present invention, a scheduled plurality of messages can be transmitted in a clear and professional manner. Additionally, “ad hoc” messages can be incorporated into the schedule without significantly disrupting the other messages.

FIELD OF THE INVENTION

The present invention relates generally to communication systems andparticularly to a method and system for scheduling and transmittingmessages.

BACKGROUND OF THE INVENTION

In-store public address systems and telephone queuing systems frequentlycommunicate with customers by playing multiple pre-recorded voicemessages throughout the day. These systems usually play static(advertising or informational) messages at set intervals which arefrequently interrupted by important or ad hoc messages (operational),which override or block the playing of static messages.

In a retail environment, the “static” messages are typicallyprofessionally recorded and may be advertisements for products orservices. The ad hoc messages are much more mundane, such as pagingpersonnel to answer a phone line, requesting a clean-up of a spilledproduct, or even advertising of in store specials or events such asannouncing to customers that in-store prepared products (fresh bakedbread or rotisserie chickens) are freshly available.

Telephone queuing systems also play advertising and informationalmessages at regular intervals. These messages are periodicallyinterrupted with status information such as expected hold times. In bothin store public address systems and telephone queuing systems,instrumental music is frequently used to fill gaps between messages. Inboth systems however, the interruption of one message to play anotherresults in a choppy presentation of all of the messages. This results ina non-professional presentation, which generally decreases theeffectiveness of both messages and can contribute to a consumer'sperception that the company is unorganized.

Accordingly, what is needed is an alternative method for queuingmessages in the above-described environments. The method should besomewhat simple, cost effective and capable of being easily adapted intoexisting technology. The present invention addresses such a need.

SUMMARY OF THE INVENTION

A method and system for scheduling and transmitting messages isdisclosed. The method and system comprise storing a plurality of audiofiles in an audio database and generating a schedule of queued messagesvia the plurality of audio files. The method and system further includestransmitting the queued messages based on the schedule and reconfiguringthe schedule based on a user interaction. The method and system finallyincludes delivering the queued messages in accordance with thereconfigured schedule.

Through the use of the method and system in accordance with the presentinvention, a scheduled plurality of messages can be transmitted in aclear and professional manner. Additionally, “ad hoc” messages can beincorporated into the schedule without significantly disrupting theother messages.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a high-level flow chart of a method in accordance with thepresent invention.

FIG. 2 depicts an example of a system in accordance with the presentinvention.

FIG. 3 is an illustration of an alternate embodiment of the presentinvention.

FIG. 3A is a flow chart for generating a schedule of messages inaccordance with the present invention.

FIG. 4 is a detailed flowchart of the method in accordance with thepresent invention.

FIG. 5 is a more detailed flowchart of the method in accordance with thepresent invention.

FIG. 6 is a flowchart that illustrates the step of processing duemessages.

FIG. 7 is a flowchart which illustrates processing overdue messages.

DETAILED DESCRIPTION

The present invention relates generally to communication systems andparticularly to a method and system for scheduling and transmittingmessages. The following description is presented to enable one ofordinary skill in the art to make and use the invention and is providedin the context of a patent application and its requirements. Variousmodifications to the preferred embodiment and the generic principles andfeatures described herein will be readily apparent to those skilled inthe art. Thus, the present invention is not intended to be limited tothe embodiment shown but is to be accorded the widest scope consistentwith the principles and features described herein.

The present invention is presented in the context of a preferredembodiment. The preferred embodiment of the present invention is amethod and system for scheduling and transmitting messages. Accordingly,the method and system implements a scheme to schedule a queue ofmessages to be played based on various criteria including, but notlimited to the priority of the message, the interruptability of themessage, the message length, message repeat parameters, etc. Through theuse of the method and system in accordance with the present invention, ascheduled plurality of messages can be transmitted in a clear andprofessional manner.

A method in accordance with the present invention may be implemented,for example, by operating a computer system to execute a sequence ofmachine-readable instructions. The instructions may reside in varioustypes of computer readable media. In this respect, another aspect of thepresent invention concerns a programmed product, comprising computerreadable media tangibly embodying a program of machine readableinstructions executable by a digital data processor to perform a methodfor scheduling and transmitting messages.

This computer readable media may comprise, for example, RAM (not shown)contained within the system. Alternatively, the instructions may becontained in another computer readable media such as a magnetic datastorage diskette and directly or indirectly accessed by the computersystem. Whether contained in the computer system or elsewhere, theinstructions may be stored on a variety of machine readable storagemedia, such as a DASD storage (e.g. a conventional “hard drive” or aRAID array), magnetic tape, electronic read-only memory, an opticalstorage device (e.g., CD ROM, WORM, DVD, digital optical tape), paper“punch” cards, or other suitable computer readable media includingtransmission media such as digital, analog, and wireless communicationlinks. In an illustrative embodiment of the invention, themachine-readable instructions may comprise lines of compiled C, C++, orsimilar language code commonly used by those skilled in the programmingfor this type of application arts.

The plurality of messages upon which the schedule is generated,preferably comprises “static” advertising messages (corporate sponsoredmessages for various products and/or services) and local advertisingmessages (in store specials or events such as announcing to customersthat in-store prepared products are freshly available). Each of thesemessages would typically have a relevant set of times that they will beplayed as well as a target number of repeats.

In addition, actual delivery statistics may be collected. Thisinformation might be used to bill vendors for a per-delivery advertisingcost which may vary based upon the time of day that the message isplayed. A rule might also be set which indicates that interruptedmessages are not counted as played, and be re-queued for later delivery.

However, when “ad hoc” messages are employed, the schedule must bereconfigured to incorporate the message. Ad hoc messages are messagesprompted by a system user and can comprise instructions (“Maintenance,wet spill in aisle 10”) and/or announcements (“Freshly baked bread isnow available in the bakery”). Accordingly, when ad hoc messages areinitiated, the queuing system is responsible for reconfiguring theschedule if the ad hoc message may impact the generated schedule of thequeued messages. If messages subsequently become overdue based onconflicts with other messages, the system will reconfigure the queue ofmessages for a specified time frame (e.g. an hour, a day, etc.) until atime is reached when all scheduling conflicts have been resolved.

FIG. 1 depicts an example of a system 200 in accordance with the presentinvention. The system 200 preferably comprises a personal computer 212,which is provided with a telephone interface card 214 in one of itsexpansion slots (not shown) or a LAN connection which provides aninterface into an in-store announcement system. The PC 212 comprises amicroprocessor 216, a read-only memory (ROM) 218, a random access memory(RAM) 220, and a magnetic hard disk drive 221, all of which operate inconjunction with the telephone interface board 214 using a standard bus222. The PC also includes a clock 217 and conventional input/outputinterface components 224 such as serial communication ports. Themicroprocessor 216 is programmed to selectively and automatically playrecorded audio messages, which have been previously stored on preferablya hard disk 221, over a public address loudspeaker 226 that is driven bya public address amplifier 228. The amplifier 228 can be connected tothe PC 212 by a conventional telephone line 229 using the telephoneinterface board 214. The telephone line 229 is preferably coupled to thetelephone interface board 214 via an interface ciruit 215. One or moreconventional telephones or other devices (cash registers, other computersystems, etc.) can be connected to the PC through a private branchexchange (PBX). Current technology may enable the connection via LANattachments.

The system 200 is also provided with a display device 223 (e.g., a videomonitor or LED display screen) and a keyboard 225 connected to the bus222. The keyboard can be used to enter graphic or alphanumeric messagesto be stored and displayed on the display device 223, as well as toperform system functions such as reviewing, modifying or deletinggraphic messages or entering data for scheduling message play times.Alternatively, another type of input device can be employed, forexample, to store video signals for generation on the display device 223in accordance with the present invention.

The system may also include a plurality of Application ProgrammingInterfaces 234 (APIs) that can interact with the system. Theseinterfaces can also interact with other systems that are coupled to thesystem 200. For example, DLLs or remote procedure calls may be providedwhich may be used to create a new user interface into the system, or mayallow batch processing of input to queue new messages, or report onentries within the system.

FIG. 2 is a block diagram illustrating a plurality of logical components234 that interact with the system 200. An implementation of thesecomponents would likely use the API to update the system. Theseinterfaces include, but are not limited to, a composite message editor302, a generic scheduler 304, a schedule validator/optimizer 306, afeedback editor 308, a feedback receiver 310, a security interface 312and a message consistency checker 314. These interfaces will bedescribed in detail hereinbelow.

Composite Message Editor 302

The composite message editor is an interface which allows the user todefine the message segments and rules associated with creating acomplete message. The composite message editor applies these rules toensure that the message can be properly constructed based upon the rulesdefined for a message to ensure that the composite message componentparts are available. The composite message editor minimally includes theability to save/edit/delete messages. These actions may further beexported to another system.

Generic Scheduler 304

The generic scheduler is a module which allows a user to define scheduletimes including repeats. The user is provided the ability to save theschedule for later use when queuing in messages. This enables the userto associate an audio message with the schedule rather than maintainingunique schedule data for each message.

Schedule Validator/Optimizer 306

The schedule validator/optimizer validates and optimizes the schedule ofthe various messages. This interface allows the user to “check” theschedule of queued messages to inspect the level of calculated overlapor collision between messages. The optimizer could recommend changes tothe schedule in order to reduce the number of collisions. The queuingsystem itself handles collisions by sorting the colliding messages bypriority and playing them serially. However this interface allows theuser to review the set of scheduled messages in order to determine ifthere are too many periods of high collisions, or if the scheduling issuch that ad-hoc messages would create significant disturbances in theschedule.

Feedback Editor 308

The feedback editor is a component which leads a user through theprocess of defining the various specifics related to obtaining feedback.(Feedback is discussed further herein below.)

Feedback Receiver 310

The feedback receiver receives the feedback results from the system. Ina simple case the data is simply stored in a database for later use ormay be dumped into a file.

Security Interface 312

The security interface comprises security methods or processes in orderto assign accountability of actions to the logged in user, and thereforeprotect the business image. Due to the nature of this system, thereshould be varying levels of security for each of the various methods ofinputting data into this system. The specific security measures employedwill vary from implementation to implementation.

Message Consistency Checker 314

A message consistency checker can be provided to ensure that all of thevarious message components are available within the system. Basically,this function performs a consistency check on the various tables of thedatabase to determine what tables refer to entries in other tables thatdo not exist. These results are reportable both locally and remotely.

Logging 316

All significant actions within the system should be logged to an auditlog to provide for an audit of the system as well as to assist supportof the system. This is a basic requirement of any computer based system.The details of the amount of data logged and the format of the datalogged may be dependent on several factors, but such detail is notmaterial to this disclosure.

In-Store Telephone Access 318

The In-Store telephone access will allow a user to queue a message viaselecting the initial category of the message, then, the individualvariable components of the message. Note that in order to support thissort of function, the user could be required to key enter differentcodes in the system to select the various message components. In thebest implementation, the access system will contain an audio recordingwhich describes the category and selection options for the variousvariable portions of the audio message. In an ideal implementation, inorder to facilitate ease of use and reduce the effort required tocomplete the component parts of the message, different component partsmight be maintained.

For instance, the “maintenance cleanup” message above might bemaintained in the system, but there might also be a table in thedatabase which allows a composite message to define another compositemessage while specifying some of the variable parts, for instance,creating a “dry spill” message, and a “wet spill” message by utilizingthe main components of the “maintenance cleanup” message.

Telephone based access is an important component of the system as itprovides an inexpensive interface into the system at various locationsthroughout the store, without requiring hardware installations at thoselocations where a telephone is already installed.

In-Store Advertising Module, Regional Advertising Module, CorporateAdvertising Module 320

The advertising modules are distinct modules within the system, eachwith different rules applied to determining how to queue messages. Inthe most basic implementation, the In-Store module allows queuing of asubset of messages, and allows adding trivia messages to the system. Theregional and corporate modules include more advanced function, such assetting up to obtain feedback from the shoppers in the store, and mayinclude more advanced tie-ins to other systems with this feedback.

The feedback obtained may be used in several ways. The retailer alreadyknows how many customers and dollars worth of sales volume occur at eachstore by reviewing sales data information, but may be interested indetermining other information related to the advertising.

Using such a system, the retailer might be able to determine the reachof advertising to mobile device users simply by requestingidentification by the device as feedback to all mobile devices in thestore at the time that the advertisement is played. The advertisementmay then be evaluated by tracking the sales of the customers present todetermine if the advertisement produced results. In this case, thefeedback did not include a prompt for information from the user; themobile device could service the request without user interaction.

In a preferred embodiment, the Corporate and Regional advertisingmodules should support an easy export of data to facilitate transmissionof the scheduled messages to remote locations.

API Access 322

APIs written for this system should be written with the intent ofcreating an application developer's interface into the system to allowfor quick application development and ease of use.

The APIs are intended to be the basis of all development work related tothe system. In an actual implementation, it is expected that there maybe several special purpose programs at a single retailer's location,which are designed to queue only a subset of messages and may betailored to the retailer's specific environment. The need for this isdriven by the usually unique needs of different retailers based uponoperational differences. Further, the responsibilities of those personsperforming different jobs within the store will have different uses ofthe system.

In general, the API access should, but does not need to allow fulladministration of the system.

A sensible system design would include use of the APIs by each of theabove modules which are expected to be a part of the system.

The underlying architecture of the API is not material to thisdisclosure. A preferred embodiment of the architecture will takeadvantage of the use of a routable protocol to allow use of the same APIset for local access as for remote access.

In a preferred embodiment, emerging technologies such as XML and SimpleObject Access Protocol (SOAP) with attachment could be used to supportall messaging within the system. Audio files may be transmitted in aSOAP message as an attachment.

Since the APIs are intended to provide the application developer withmost if not all of the functions required to maintain the system, thefollowing are examples of the types of functions which most likelyshould be included in the API:

-   -   Add/Erase/Update each of the database tables

(Note that some of these functions may be provided via interfaces intothe database directly, but since not all users should have direct accessinto the database, it is expected that the API will provide the accessinto the database to ensure that the system rules are enforced.)

-   -   Add/Erase/Update of feedback instructions    -   Add/Erase/Update of queued messages

Even though this function will most likely result in a table update forthe database, this function is listed separately since the function ismore specific than simply updating an audio clip in the database.

-   -   Validation functions

Referring back to FIG. 1, preferably, the system 200 further includes anaudio database 320 for storing an archive of audio files. The audiodatabase 227 could be located in the hard disk 221, the ROM 218 oranother suitable location in the computer 212. In this embodiment, theaudio database 227 is located in the ROM 218. The audio database 227maintains a table of the audio files wherein the table includesinformation related to the audio file, e.g. the category of the file,the length of the file, a short description of the file, an index numberof the file, etc.

FIG. 3 is a high level flowchart of the method in accordance with thepresent invention. First, a plurality of audio files is stored in anaudio database, via step 350. A schedule of messages is then generatedvia the plurality of audio files, via step 360. Generating the scheduleof messages must be accomplished by building the messages in accordancewith a schedule profile.

FIG. 3A is a flow chart for generating a schedule of messages inaccordance with the present invention. Referring to the Figure, first amessage structure is built, via step 352. Next, a schedule profile forthe audio files is built, via step 354. Thereafter, a message isassociated with the schedule profile, via step 356. Accordingly, theschedule of messages is generated.

Referring back to FIG. 3, the queued messages are then transmitted basedon the schedule, via step 370. Next, the schedule is reconfigured basedon a user interaction, via step 380. Finally, the queued messages aredelivered in accordance with the reconfigured schedule.

By way of example, an audio file requesting a manager to come to thecustomer service counter might be a professionally recorded “wav” filefeaturing a pleasant sounding woman's voice saying the words “storemanager needed at customer service for customer assistance”. Thecategory might be “Store Operations Announcement”; the description mightbe “Manager report to customer service”.

Additionally, the audio file could be a composite message. A compositeaudio message is an audio message which is made up of variouscomponents. A composite audio message might be a single audio clip fromthe audio database, but could in fact be a combination of messagecomponents that are selected based on a user interaction. The compositemessage could be expressed in the database as a set of static andvariable components. For example, the message “Maintenance, pleasereport to aisle 3 for a dry spill clean-up.” can be broken down into thefollowing components: “Maintenance, please report to” Static “aisle”Variable “3” Variable “for a “ Static “dry spill” Variable “cleanup”StaticThe static audio clips are selections from the audio database, but toconstruct a “store cleanup” message, these components are always fixed.The three selectable components are selected by a user preferably via atelephone/keypad type device. The resulting composite messageaccordingly comprises the specific static message components as well asthe selected variable components. It should be appreciated by one ofordinary skill in the art that the selection of the variable componentsof the message could be designed to conform to a set of predeterminedrules that govern their selection.

Composite messages are preferably utilized to allow a user to queue the“ad hoc” messages. This is preferably accomplished via atelephone/keypad-type device whereby an initial category of the messageis selected and then the individual variable components of the messageare selected. Note that in order to support this sort of function, theuser could be required to key enter different codes in the system toselect the various message components. For example, an access systemutilized by the keypad-type device to access the audio database couldcontain an audio clip which describes the category and selection optionsfor the various variable portions of an audio message.

All queued messages include a complete audio message, all necessaryscheduling attributes, and feedback instructions. A message cannot bequeued without all of the data required by the queuing system.Furthermore, all of the message components should be available prior toqueuing. It is possible to queue messages which are comprised ofseparate components (such as queuing a static message with no feedback).In these cases the attributes are defined but have no actions associatedwith them.

If the system attempts to queue a message for which all of thecomponents are not available, the message is not queued and errorinformation is returned to the user. In order to avoid this situation,the system also includes functions to assist in validating that all ofthe components for a given message are available and should be able toprovide a sufficient amount of information to identify the problem andperform an appropriate corrective action. End user application programsdesigned to interface with this system should appropriately prompt theuser for the required information in order to minimize the chance oferror and optimize the usability of the queued message.

Another feature of the present invention involves the addedfunctionality of generating feedback from the scheduled transmission ofmessages. Feedback is any data collected as a result of prompting forinformation related to an audio message. The information could berelated to advertised products, including special offers for storeproducts or the information could be related to ad hoc messages, e.g.whether a store manager has responded to earlier page. In order toinclude this functionality, the above-described system must includefeedback device(s) coupled thereto.

FIG. 4 is an illustration of an alternate embodiment of the presentinvention. The alternate embodiment includes the system 200 from FIG. 3;however the system 200 is coupled to a plurality of feedback devices410, 420, 430. These devices could comprise cell-phones, PersonalDigital Assistants (PDA's), a kiosk, etc. These devices could bewirelessly coupled to the system 200 (cell phone, PDA) or hard wiredinto the system 200 (kiosk). One of ordinary skill in the art willreadily appreciate that a variety of devices could be utilized whileremaining within the spirit and scope of the present invention.

FIG. 5 is a more detailed flowchart of the method in accordance with thepresent invention. First, the system checks for newly queued messages,via step 505. If a newly queued message exists, the schedule isreconfigured, via step 510. Either after step 510 or if a newly queuedmessage does not exist, the current schedule is checked for duemessages, via step 513. If there are due messages, they are processedvia step 514. Either after step 514 or if there are no due messages, thecurrent schedule is checked for overdue messages via step 515. Next, theoverdue messages are processed via step 517 and then return to step 505.If there are no overdue messages, return to step 505. Processing of thedue and overdue messages is important to provide the feedback requiredto schedule and transmit the messages at the appropriate time. Thefollowing description, along with accompanying figures, will describeprocessing due and overdue messages in more detail.

FIG. 6 is a flowchart that illustrates the step of processing duemessages, step 514 of FIG. 5. First the message is played, via step 602.Next, it is determined if feedback is requested, via step 604. If thereis no feedback requested, then the process ends, via step 610. Iffeedback is requested, then it is obtained, via step 606, and processed,via step 608. Thereafter, the process ends.

FIG. 7 is a flowchart which illustrates processing overdue messages,STEP 517 of FIG. 5. First, if a message is overdue, it is determined ifthe overdue message should be played at this time, via step 702. If amessage should be played, then the procedure is executed for processingdue messages as in FIG. 6, via step 704. If the answer is no, or afterstep 704, it is then determined whether the overdue message should berescheduled, via step 706. Immediately playing the overdue message maybe desired, for example (step 704). Thereafter, if the message wassupposed to be played at a critical time (such as the prime time ofactivity), the message may be rescheduled to be played during that time(step 706).

If a message should be rescheduled, then the schedule attributes shouldbe modified according to rule and reschedule message, via step 708. Theschedule attributes, for example, could be priority, schedule,frequency, etc. of the message. Either after step 708 or if the answerto rescheduling a message is no, then it is determined if there areother overdue actions associated with this message, via step 709. If theanswer is no, then that is the end of the process. If the answer is yes,then the other overdue actions should be executed, via step 710.Thereafter, the process ends.

An inherent assumption regarding the ability to receive feedback from adevice is the device's ability to receive the command and respond to it.For instance, a customer's cell phone might need to not only join thestore's local area network (cell phone's PAN), but may also need todownload a module which facilitates this sort of communication with thesystem 200 (FIG. 1).

Once the feedback is received, the system needs to know what to do withit. The data could be collected and sent as a results set over a socketto another system, collected and stored in a table in the systemdatabase for future processing, etc. Once the data is sent to theappropriate receiver, a process may be started either locally orremotely for processing the data.

To illustrate, consider the following examples: A service area mightqueue an immediate message to the system via a PC which causes a messageto be played requesting the manager's presence at in the customerservice area. The feedback for this message is a prompt 30 seconds laterwhich asks if the manager has arrived. If the manager has not arrived(clerk responds negatively), or a response to the prompt is not receivedin a timeout period (perhaps defined as 10 seconds), the message isrequeued.

-   -   Advertisement is played once an hour in the store for a brand of        potato chips. At that time, customers' cell phones & PDA's are        prompted and queryed as to whether they would like to receive an        automatic discount on the item at checkout, if they respond yes,        feedback is queued to a front end system to queue the coupon.        Additionally, if the customer has not selected to receive the        discount, but enters the zone of the store where the product is        located, the system might prompt again asking if they would like        to receive a discount on the item.    -   A customer leaves a perishable item at the front end with a        cashier, which they have decided not to purchase. The cashier        may queue a message for a person from the department to collect        the item and return it to its sales location. The ad hoc message        could be queued with the department name as a variable message        component, or if there is not staffing in the department, a        manager might be paged. After a few minutes the cashier could be        prompted by the system in order to ascertain if the item has        been collected. If it hasn't, the system would repeat the page.

A method and system for scheduling and transmitting messages isdisclosed. Accordingly, the method and system implements a scheme toschedule a queue of messages to be played based on various criteriaincluding, but not limited to the priority of the message, theinterruptability of the message, the message length, message repeatparameters, etc. Through the use of the method and system in accordancewith the present invention, a scheduled plurality of messages can betransmitted in a clear and professional manner.

Although the present invention has been described in accordance with theembodiments shown, one of ordinary skill in the art will readilyrecognize that there could be variations to the embodiments and thosevariations would be within the spirit and scope of the presentinvention. Accordingly, many modifications may be made by one ofordinary skill in the art without departing from the spirit and scope ofthe appended claims.

1. A method for scheduling and transmitting messages comprising thesteps of: a) storing a plurality of audio files in an audio database; b)generating a schedule of queued messages via the plurality of audiofiles; c) transmitting the queued messages based on the schedule; d)reconfiguring the schedule based on a user interaction; and e)delivering the queued messages in accordance with the reconfiguredschedule.
 2. The method of claim 1 wherein each message comprises aplurality of attributes and the schedule is generated based on theplurality of attributes.
 3. The method of claim 2 wherein step d)further comprises: d1) utilizing the plurality of audio files togenerate an ad-hoc message based on the user interaction; and d2)reconfiguring the schedule based on a priority level of the ad-hocmessage.
 4. The method of claim 3 wherein the user interaction isinitiated via a keypad based device.
 5. The method of claim 4 whereinthe keypad based device comprises a computer.
 6. The method of claim 4wherein the keypad based device comprises a telephone.
 7. The method ofclaim 1 in which the generating step (b) comprises the steps of: (b1)building a message structure; (b2) building a schedule profile for theplurality of audio files; and (b3) associating a message with theschedule profile.
 8. The method of claim 1 in which the transmittingstep (e) includes the steps of: (e1) checking for due messages; (e2)processing due messages if appropriate; (e3) checking for overduemessages; and (e4) processing the overdue messages if appropriate. 9.The method of claim 8 wherein processing due messages step (e2)comprises the steps of: (e21) playing the message; (e22) determining iffeedback is requested; (e23) obtaining the requested feedback; and (e24)processing the feedback.
 10. The method of claim 8 wherein processingoverdue messages step (e3) comprises the steps of: (e31) determining ifoverdue message should be played; (e32) processing the overdue messageas a due message if it is to be played; (e33) determining if the overduemessage should be rescheduled; (e34) modifying schedule attributesaccording to rescheduled message; (e35) determining if there are otheroverdue actions associated with the rescheduled message; and (e36)executing the other overdue actions if appropriate.
 11. A programmableaudio message system comprising: an audio database for storing aplurality of audio files; a scheduling mechanism coupled to the audiodatabase for generating a schedule of queued messages via the pluralityof audio files; transmission means coupled to the scheduling mechanismfor transmitting the queued messages based on the schedule; and areconfiguring mechanism coupled to the scheduling mechanism fordelivering the queued messages in accordance with the reconfiguredschedule.
 12. The programmable audio message system of claim 11 whereineach message comprises a plurality of attributes and the schedule isgenerated based on the plurality of attributes.
 13. The programmableaudio message system of claim 12 wherein the reconfiguring mechanismcomprises a plurality of interfaces for utilizing the plurality of audiofiles to generate an ad-hoc message based on the user interaction andfor reconfiguring the schedule based on a priority level of the ad-hocmessage.
 14. The programmable audio message system of claim 13 whereinthe user interaction is initiated via a keypad based device.
 15. Theprogrammable audio message system of claim 14 wherein the keypad baseddevice comprises a computer.
 16. The programmable audio message systemof claim 15 wherein the keypad based device comprises a telephone. 17.The programmable audio message system of claim 11 in which thescheduling mechanism comprises: means for building a message structure;means for building a schedule profile for the plurality of audio files;and means for associating a message with the schedule profile.
 18. Theprogrammable audio message system of claim 11 in which the reconfiguringmechanism comprises: means for checking for due messages; means forprocessing due messages if appropriate; means for checking for overduemessages; and means for processing overdue messages if appropriate. 19.The system of claim 18 wherein processing due messages step meanscomprises: means for playing the message; means for determining iffeedback is requested; means for obtaining the requested feedback; andmeans for processing the feedback.
 20. The system of claim 18 whereinprocessing overdue messages means comprises: means for determining ifoverdue message should be played; means for processing the overduemessage as a due message if it is to be played; means for determining ifthe overdue message should be rescheduled; means for modifying scheduleattributes according to rescheduled message; means for determining ifthere are other overdue actions associated with the rescheduled message;and means for executing the other overdue actions if appropriate.
 21. Acomputer readable medium comprising program instructions for schedulingand transmitting messages, the program instructions comprising the stepsof: a) storing a plurality of audio files in an audio database; b)generating a schedule of queued messages via the plurality of audiofiles; c) transmitting the queued messages based on the schedule; d)reconfiguring the schedule based on a user interaction; and e)delivering the queued messages in accordance with the reconfiguredschedule.
 22. The computer readable medium of claim 21 wherein eachmessage comprises a plurality of attributes and the schedule isgenerated based on the plurality of attributes.
 23. The computerreadable medium of claim 22 wherein step d) further comprises: d1)utilizing the plurality of audio files to generate an ad-hoc messagebased on the user interaction; and d2) reconfiguring the schedule basedon a priority level of the ad-hoc message.
 24. The computer readablemedium of claim 23 wherein the user interaction is initiated via akeypad based device.
 25. The computer readable medium of claim 24wherein the keypad based device comprises a computer.
 26. The computerreadable medium of claim 24 wherein the keypad based device comprises atelephone.
 27. The computer readable medium of claim 21 in which thegenerating step (b) comprises the steps of: (b1) building a messagestructure; (b2) building a schedule profile for the plurality of audiofiles; and (b3) associating a message with the schedule profile.
 28. Thecomputer readable medium of claim 21 in which the transmitting step (e)includes the steps of: (e1) checking for due messages; (e2) processingdue messages if appropriate; (e3) checking for overdue messages; and(e4) processing the overdue messages if appropriate.
 29. The computerreadable medium of claim 21 wherein processing due messages step (e2)comprises the steps of: (e21) playing the message; (e22) determining iffeedback is requested; (e23) obtaining the requested feedback; and (e24)processing the feedback.
 30. The computer readable medium of claim 21wherein the processing overdue messages step (e3) comprises the stepsof: (e31) determining if overdue message should be played; (e32)processing the overdue message as a due message if it is to be played;(e33) determining if the overdue message should be rescheduled; (e34)modifying schedule attributes according to rescheduled message; (e35)determining if there are other overdue actions associated with therescheduled message; and (e36) executing the other overdue actions ifappropriate.
 31. A method for scheduling and transmitting messagescomprising the steps of: a) storing a plurality of audio files in anaudio database; b) generating a schedule of queued messages via theplurality of audio files wherein at least one of the queued messagescomprises a prompt to obtain feedback; c) transmitting the queuedmessages based on the schedule; d) obtaining the feedback related to theprompt; and e) processing the obtained feedback.
 32. The method of claim31 wherein each message comprises a plurality of attributes and theschedule is generated based on the plurality of attributes.
 33. Aprogrammable audio message system comprising: an audio database forstoring a plurality of audio files; scheduling means coupled to theaudio database for generating a schedule of queued messages via theplurality of audio files; transmission means coupled to the schedulingmechanism for transmitting the queued messages based on the schedule;reconfiguring means coupled to the scheduling mechanism forreconfiguring the schedule based on a user interaction; feedbackobtaining means for obtaining feedback related to the transmission ofthe queued messages.
 34. The system of claim 33 further comprises atleast one feedback device coupled to the system for receiving thetransmission of the queued messages and producing feedback related tothe transmission of the queued messages.
 35. The system of claim 33further comprises feedback processing means coupled to the feedbackobtaining means.
 36. The system of claim 35 wherein the at least onefeedback device comprises a PDA.
 37. The system of claim 35 wherein theat least one feedback device comprises a cell phone.
 38. The system ofclaim 35 wherein the at least one feedback device comprises a kiosk. 39.A computer readable medium comprising program instructions forscheduling and transmitting messages, the program instructionscomprising the steps of: a) storing a plurality of audio files in anaudio database; b) generating a schedule of queued messages via theplurality of audio files wherein at least one of the queued messagescomprises a prompt to obtain feedback; c) transmitting the queuedmessages based on the schedule; d) obtaining the feedback related to theprompt; and e) processing the obtained feedback.
 40. The computerreadable medium of claim 39 wherein each message comprises a pluralityof attributes and the schedule is generated based on the plurality ofattributes.